Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c07c4d29c84fb9682dcb64dd2f7164e7fb1d6101ca7bdeea5cfaf49679e530c

Tx prefix hash: 87032f1cb73c007db1d371804b64113722c7bc759f8a74ba2bbfbfcb634e65b1
Tx public key: 3c1827ae9d8595e25dd5fb66071bad62fadd2287e3b416047c6312bf229c9caa
Timestamp: 1746797496 Timestamp [UCT]: 2025-05-09 13:31:36 Age [y:d:h:m:s]: 00:195:19:59:59
Block: 1279184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137670 RingCT/type: yes/0
Extra: 013c1827ae9d8595e25dd5fb66071bad62fadd2287e3b416047c6312bf229c9caa0211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b536fcc8b5c5ed78a89b00ebd62ba8942817e0d453f700a405c8c0454db9aefe 0.600000000000 1766557 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": 1279194, "vin": [ { "gen": { "height": 1279184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b536fcc8b5c5ed78a89b00ebd62ba8942817e0d453f700a405c8c0454db9aefe" } } ], "extra": [ 1, 60, 24, 39, 174, 157, 133, 149, 226, 93, 213, 251, 102, 7, 27, 173, 98, 250, 221, 34, 135, 227, 180, 22, 4, 124, 99, 18, 191, 34, 156, 156, 170, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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