Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27257c2bed77443b8c09d1c56b471eb6fb2df2bd6b7e4f600cde1026981a1d31

Tx prefix hash: 6570e3b4ac7680afaf0a242de6b71b75d305a134cbeeb4ee335d7bf6e7711b56
Tx public key: f72d48f80764a86ab0335f238a94c8949606fb7748b22f1089fed0e538e2266a
Timestamp: 1756453751 Timestamp [UCT]: 2025-08-29 07:49:11 Age [y:d:h:m:s]: 00:129:15:09:28
Block: 1356811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92700 RingCT/type: yes/0
Extra: 01f72d48f80764a86ab0335f238a94c8949606fb7748b22f1089fed0e538e2266a021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd6b8eaeab576ab6608f13ac634adab2e446934f4f5f18d8a1c9a65393d074a1 0.600000000000 1844820 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": 1356821, "vin": [ { "gen": { "height": 1356811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd6b8eaeab576ab6608f13ac634adab2e446934f4f5f18d8a1c9a65393d074a1" } } ], "extra": [ 1, 247, 45, 72, 248, 7, 100, 168, 106, 176, 51, 95, 35, 138, 148, 200, 148, 150, 6, 251, 119, 72, 178, 47, 16, 137, 254, 208, 229, 56, 226, 38, 106, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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