Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b075cada67d980372c5cd41ccadbbaeb6364027e9410430f0d69eeccdc76d69f

Tx prefix hash: 4e4808c8997442c1e907b5375ae54d843c1d2df617d0494190701b9e6f51cdfc
Tx public key: d4976f665002186caa7cd19f022b5c593458d5adc168741b31ee8a7e6c4a6fd6
Timestamp: 1712605032 Timestamp [UCT]: 2024-04-08 19:37:12 Age [y:d:h:m:s]: 01:031:14:07:21
Block: 996219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283569 RingCT/type: yes/0
Extra: 01d4976f665002186caa7cd19f022b5c593458d5adc168741b31ee8a7e6c4a6fd60211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fd52cfe72cf4407895709dc8c1adb86c79bf822ea86e48ebde0dfe33a885ef9 0.600000000000 1456635 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": 996229, "vin": [ { "gen": { "height": 996219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fd52cfe72cf4407895709dc8c1adb86c79bf822ea86e48ebde0dfe33a885ef9" } } ], "extra": [ 1, 212, 151, 111, 102, 80, 2, 24, 108, 170, 124, 209, 159, 2, 43, 92, 89, 52, 88, 213, 173, 193, 104, 116, 27, 49, 238, 138, 126, 108, 74, 111, 214, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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