Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88dcfc5afa937830d1f9e722e4fbed11430d78c3e63152394294d8424032bf60

Tx prefix hash: 81170cf5e7ab64eaace86c5a7eec83ae94fde6b0938321498aa6bce55587815e
Tx public key: 4678fef1a1e96a523f894d6de550fedbcf88a59ff55894822fd6fb7c6de7335d
Timestamp: 1704795561 Timestamp [UCT]: 2024-01-09 10:19:21 Age [y:d:h:m:s]: 01:070:00:22:38
Block: 931490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311158 RingCT/type: yes/0
Extra: 014678fef1a1e96a523f894d6de550fedbcf88a59ff55894822fd6fb7c6de7335d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 769ccaf0c436c0ab5f4378a2d420ebe416d4fe017f1f1b30aea8b82f62536add 0.600000000000 1389392 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": 931500, "vin": [ { "gen": { "height": 931490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "769ccaf0c436c0ab5f4378a2d420ebe416d4fe017f1f1b30aea8b82f62536add" } } ], "extra": [ 1, 70, 120, 254, 241, 161, 233, 106, 82, 63, 137, 77, 109, 229, 80, 254, 219, 207, 136, 165, 159, 245, 88, 148, 130, 47, 214, 251, 124, 109, 231, 51, 93, 2, 17, 0, 0, 0, 1, 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