Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46708a39e0e1e4f8fb2bfc057d501f58afc71658ed267fdb6cf789bcc7fbf8fc

Tx prefix hash: cc37c47e764829132d1ad9371db54536b7d042bcbeab35a89dc222ded7e91f88
Tx public key: b6723cd334811b4ef49a86d8fec80e0df987cadc1dbe758d1c8407cf73776bfd
Timestamp: 1737856045 Timestamp [UCT]: 2025-01-26 01:47:25 Age [y:d:h:m:s]: 00:146:23:28:23
Block: 1205393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104729 RingCT/type: yes/0
Extra: 01b6723cd334811b4ef49a86d8fec80e0df987cadc1dbe758d1c8407cf73776bfd021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 607a51e50b737d0b23b4f0c4ddd0b9c1279c749c0d271e301c076c8f51cee22b 0.600000000000 1692090 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": 1205403, "vin": [ { "gen": { "height": 1205393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "607a51e50b737d0b23b4f0c4ddd0b9c1279c749c0d271e301c076c8f51cee22b" } } ], "extra": [ 1, 182, 114, 60, 211, 52, 129, 27, 78, 244, 154, 134, 216, 254, 200, 14, 13, 249, 135, 202, 220, 29, 190, 117, 141, 28, 132, 7, 207, 115, 119, 107, 253, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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