Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36b6e314084435ae5e7bd98ec81a9bd68973b33d5575a567fd11b2dd55747e75

Tx prefix hash: 4f93848f988947574186ae1a96f8d3760e7f9d029166140b80e467f8898f4a52
Tx public key: b5ba9336f5d5acd4e48adaf6c991aac91fe55413457283735e028ab5d57b3ad8
Timestamp: 1706494731 Timestamp [UCT]: 2024-01-29 02:18:51 Age [y:d:h:m:s]: 01:297:07:21:22
Block: 945558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471302 RingCT/type: yes/0
Extra: 01b5ba9336f5d5acd4e48adaf6c991aac91fe55413457283735e028ab5d57b3ad802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 510132b8e81a5a9c2a33acd7589c7a39e5e7cc3d666dcd5d4df8b36ac7af455e 0.600000000000 1403874 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": 945568, "vin": [ { "gen": { "height": 945558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "510132b8e81a5a9c2a33acd7589c7a39e5e7cc3d666dcd5d4df8b36ac7af455e" } } ], "extra": [ 1, 181, 186, 147, 54, 245, 213, 172, 212, 228, 138, 218, 246, 201, 145, 170, 201, 31, 229, 84, 19, 69, 114, 131, 115, 94, 2, 138, 181, 213, 123, 58, 216, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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