Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93e7cd9f5fa14d14157078cfe0ef096020fc18b9c5a7173d889994128a16c440

Tx prefix hash: ae38b3010168a689372d235ffd8f84a9220eb1b8d262cface2c7315ed403c440
Tx public key: fd44525e325b7875da3c628aa04aa33c58103faba3c1804e468529765b7dbe2b
Timestamp: 1705855309 Timestamp [UCT]: 2024-01-21 16:41:49 Age [y:d:h:m:s]: 01:287:07:59:05
Block: 940259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464168 RingCT/type: yes/0
Extra: 01fd44525e325b7875da3c628aa04aa33c58103faba3c1804e468529765b7dbe2b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 313cc7256a9f2dd33a71f69eeaf55e36002e7eb913428aaff4ce7c29f3f0de0a 0.600000000000 1398395 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": 940269, "vin": [ { "gen": { "height": 940259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "313cc7256a9f2dd33a71f69eeaf55e36002e7eb913428aaff4ce7c29f3f0de0a" } } ], "extra": [ 1, 253, 68, 82, 94, 50, 91, 120, 117, 218, 60, 98, 138, 160, 74, 163, 60, 88, 16, 63, 171, 163, 193, 128, 78, 70, 133, 41, 118, 91, 125, 190, 43, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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