Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6580a6f5c28cbda3d386c3cea80d1eaa4d0c34004456c5017559ea37cb21b87

Tx prefix hash: 8acd2f9ada7f915a2ada8d77b1fe28f3d1f500bc3beaab76ae7e36d8d7e6bc5a
Tx public key: 170ee40428e61b43167d54792db01b50291d44ef7a8591163abe95acf257d4db
Timestamp: 1727817717 Timestamp [UCT]: 2024-10-01 21:21:57 Age [y:d:h:m:s]: 00:113:02:39:46
Block: 1122375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80822 RingCT/type: yes/0
Extra: 01170ee40428e61b43167d54792db01b50291d44ef7a8591163abe95acf257d4db02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd81df36a8a44e3a4f7b124e464a9a7ad28d6464f0800d26c3724f6f46ec691b 0.600000000000 1604800 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": 1122385, "vin": [ { "gen": { "height": 1122375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd81df36a8a44e3a4f7b124e464a9a7ad28d6464f0800d26c3724f6f46ec691b" } } ], "extra": [ 1, 23, 14, 228, 4, 40, 230, 27, 67, 22, 125, 84, 121, 45, 176, 27, 80, 41, 29, 68, 239, 122, 133, 145, 22, 58, 190, 149, 172, 242, 87, 212, 219, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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