Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395dbefce265f23f336820cd05e5a6c16fd6c7d27e93d433b1cc815087c2b455

Tx prefix hash: 653754ad04fac874ea4d9e1824eb93db169d2192661aa5c1f690a715fb001f8c
Tx public key: d4b661660c2573bcd747d7375f6b4decfea5fe01a59eaaccaed4b454e8684cb3
Timestamp: 1737864411 Timestamp [UCT]: 2025-01-26 04:06:51 Age [y:d:h:m:s]: 00:330:08:55:06
Block: 1205454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233716 RingCT/type: yes/0
Extra: 01d4b661660c2573bcd747d7375f6b4decfea5fe01a59eaaccaed4b454e8684cb3021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b72f1b236352d60ff3419fbc9ca0e3e51ec751a1d0514a15b2d0bfda4911932 0.600000000000 1692151 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": 1205464, "vin": [ { "gen": { "height": 1205454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b72f1b236352d60ff3419fbc9ca0e3e51ec751a1d0514a15b2d0bfda4911932" } } ], "extra": [ 1, 212, 182, 97, 102, 12, 37, 115, 188, 215, 71, 215, 55, 95, 107, 77, 236, 254, 165, 254, 1, 165, 158, 170, 204, 174, 212, 180, 84, 232, 104, 76, 179, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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