Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a37e5d364848499ca386dbfb6faa3bad20ddcec816947773000ab4624e83c470

Tx prefix hash: 33dcd2310f1338221909612e9fbaee70dc317ff4ec77358e9a473bab5743d5cb
Tx public key: e81f6700f02336a4aa5d55a626ea8afa9c4071b6f41c18550178e6557e5fe430
Timestamp: 1703092739 Timestamp [UCT]: 2023-12-20 17:18:59 Age [y:d:h:m:s]: 01:334:09:37:04
Block: 917405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497832 RingCT/type: yes/0
Extra: 01e81f6700f02336a4aa5d55a626ea8afa9c4071b6f41c18550178e6557e5fe4300211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4c1233d0c98329f8b39373eee2ad0bcae30216a5564f26bde77e8b4cba379c3 0.600000000000 1374979 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": 917415, "vin": [ { "gen": { "height": 917405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4c1233d0c98329f8b39373eee2ad0bcae30216a5564f26bde77e8b4cba379c3" } } ], "extra": [ 1, 232, 31, 103, 0, 240, 35, 54, 164, 170, 93, 85, 166, 38, 234, 138, 250, 156, 64, 113, 182, 244, 28, 24, 85, 1, 120, 230, 85, 126, 95, 228, 48, 2, 17, 0, 0, 0, 3, 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