Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 470234579aa40d6bfb952ec5e11c9535927556ee7054a9b8e868cc98778c416c

Tx prefix hash: b690e1f7da326d4494eda9eddfe9ee748b0438ae583de47dd230ac8e6ebac1f5
Tx public key: 9596ad1a4006b0e2fcc601f59b10ecc10c023f93fe4edc4fd28b2f7e0f01882d
Timestamp: 1754765650 Timestamp [UCT]: 2025-08-09 18:54:10 Age [y:d:h:m:s]: 00:108:23:04:03
Block: 1343664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77046 RingCT/type: yes/0
Extra: 019596ad1a4006b0e2fcc601f59b10ecc10c023f93fe4edc4fd28b2f7e0f01882d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46052ceac4dd05d61992768028f5cfc1ddfa24329efcc99cee864125b65b3bd6 0.600000000000 1831505 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": 1343674, "vin": [ { "gen": { "height": 1343664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46052ceac4dd05d61992768028f5cfc1ddfa24329efcc99cee864125b65b3bd6" } } ], "extra": [ 1, 149, 150, 173, 26, 64, 6, 176, 226, 252, 198, 1, 245, 155, 16, 236, 193, 12, 2, 63, 147, 254, 78, 220, 79, 210, 139, 47, 126, 15, 1, 136, 45, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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