Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5e1b22c03f5557341b0f148577fcb313fd38d37617bb74fe70d8cb20a444d2ad

Tx prefix hash: c0e23c06bf1cb09056441767eb09353acfa29fccb8b34a83166c2a087cb7f14c
Tx public key: 4cd3a1514c42a9de41e916f4788c3d426ce3291d499786808e7ca8c80cb0b538
Timestamp: 1732564339 Timestamp [UCT]: 2024-11-25 19:52:19 Age [y:d:h:m:s]: 00:346:18:44:35
Block: 1161620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245373 RingCT/type: yes/0
Extra: 014cd3a1514c42a9de41e916f4788c3d426ce3291d499786808e7ca8c80cb0b5380211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7ef44c859b639e5e0e81b8ec17c38adb3b2fde180280279dc0144c06e7fe42a 0.600000000000 1647275 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1161630, "vin": [ { "gen": { "height": 1161620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7ef44c859b639e5e0e81b8ec17c38adb3b2fde180280279dc0144c06e7fe42a" } } ], "extra": [ 1, 76, 211, 161, 81, 76, 66, 169, 222, 65, 233, 22, 244, 120, 140, 61, 66, 108, 227, 41, 29, 73, 151, 134, 128, 142, 124, 168, 200, 12, 176, 181, 56, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8