Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b26bd95e1bcd46f69eff15eaad9ec0bce9913d0f9c4f0d888d07c1a1ac87bc2d

Tx prefix hash: 4a0fb19d6cbab924898a710f30ba36f94bf52a741d6f9e5a449a928b1a5df4b3
Tx public key: 2bd4d3bb7f01e52dc332ec18c4d057290b3fab366a7616e7030c2bf0cdaaaf18
Timestamp: 1745914855 Timestamp [UCT]: 2025-04-29 08:20:55 Age [y:d:h:m:s]: 00:268:22:00:15
Block: 1271898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189849 RingCT/type: yes/0
Extra: 012bd4d3bb7f01e52dc332ec18c4d057290b3fab366a7616e7030c2bf0cdaaaf180211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b01bd372e48f94c1abb2ae76bf70a7882a58535784e197cafb6c43b0e9f085f8 0.600000000000 1759169 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": 1271908, "vin": [ { "gen": { "height": 1271898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b01bd372e48f94c1abb2ae76bf70a7882a58535784e197cafb6c43b0e9f085f8" } } ], "extra": [ 1, 43, 212, 211, 187, 127, 1, 229, 45, 195, 50, 236, 24, 196, 208, 87, 41, 11, 63, 171, 54, 106, 118, 22, 231, 3, 12, 43, 240, 205, 170, 175, 24, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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