Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ff84a3af34e856f2213b33a733d15036fee19b7cc2be2d3aa144163c2e59d9c

Tx prefix hash: cdc38d5ca6e9583cd98cca7a3e4caae3ed7c13dd5505076cddd4560778779850
Tx public key: bb7c249678a0044bb2986bc5b5d083472b6458ae57e70e599ff9e3082db99ab6
Timestamp: 1711317024 Timestamp [UCT]: 2024-03-24 21:50:24 Age [y:d:h:m:s]: 00:291:22:07:37
Block: 985589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208943 RingCT/type: yes/0
Extra: 01bb7c249678a0044bb2986bc5b5d083472b6458ae57e70e599ff9e3082db99ab60211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b68aa832194a89f995ae590a956318c4c7d463340ccb4c670d8bcc30840bfe02 0.600000000000 1445806 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": 985599, "vin": [ { "gen": { "height": 985589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b68aa832194a89f995ae590a956318c4c7d463340ccb4c670d8bcc30840bfe02" } } ], "extra": [ 1, 187, 124, 36, 150, 120, 160, 4, 75, 178, 152, 107, 197, 181, 208, 131, 71, 43, 100, 88, 174, 87, 231, 14, 89, 159, 249, 227, 8, 45, 185, 154, 182, 2, 17, 0, 0, 0, 2, 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