Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e96362b3e05f70e0e2833b372ca6aabc9dd3ad75f3b24e7a27ba38c842b72415

Tx prefix hash: 21dcd730b5396f67fe6d41a670a326e6b13895985bf72dd94f14917aa00ff6b3
Tx public key: 8593b9c6693f6fc3ba7016d5c7a88da13fef8bb5e88d3786de7700f7a9698543
Timestamp: 1731353272 Timestamp [UCT]: 2024-11-11 19:27:52 Age [y:d:h:m:s]: 00:012:12:28:41
Block: 1151583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8967 RingCT/type: yes/0
Extra: 018593b9c6693f6fc3ba7016d5c7a88da13fef8bb5e88d3786de7700f7a96985430211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d357d59fa7a7720a7f33453d525b6093195d54b7c3b7b2be3c12303bc36ec21c 0.600000000000 1637144 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": 1151593, "vin": [ { "gen": { "height": 1151583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d357d59fa7a7720a7f33453d525b6093195d54b7c3b7b2be3c12303bc36ec21c" } } ], "extra": [ 1, 133, 147, 185, 198, 105, 63, 111, 195, 186, 112, 22, 213, 199, 168, 141, 161, 63, 239, 139, 181, 232, 141, 55, 134, 222, 119, 0, 247, 169, 105, 133, 67, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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