Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5059dfd51e95efe601ec1e7a9377bb95387f53bfdfe042c6df2ea53f95a1301

Tx prefix hash: 248d8a53f36d4a5ab0bf1a9b73616e9e0f5f5b515166edad1d81058bfddd4c52
Tx public key: c2ddc8a6b045e1444a6f0df1f826440c36fe1f263d53d58383f9da8c01c27535
Timestamp: 1744195630 Timestamp [UCT]: 2025-04-09 10:47:10 Age [y:d:h:m:s]: 00:031:19:13:18
Block: 1257655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22739 RingCT/type: yes/0
Extra: 01c2ddc8a6b045e1444a6f0df1f826440c36fe1f263d53d58383f9da8c01c275350211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a0490eff0080ce46a1acbafd0dd491504da308f1c64c214c630b0b09e25f150 0.600000000000 1744782 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": 1257665, "vin": [ { "gen": { "height": 1257655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a0490eff0080ce46a1acbafd0dd491504da308f1c64c214c630b0b09e25f150" } } ], "extra": [ 1, 194, 221, 200, 166, 176, 69, 225, 68, 74, 111, 13, 241, 248, 38, 68, 12, 54, 254, 31, 38, 61, 83, 213, 131, 131, 249, 218, 140, 1, 194, 117, 53, 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