Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b06b30ca4a692856a61f9f90fafc07d8a6f2ec6bd3af8857bd287bfaa877960a

Tx prefix hash: 04654b30f69974883618bd0da0c24047e7331ae77375dbb6d42f249c619f3419
Tx public key: ea53b294c80edc3e9dc91ceb4a2ada633962ea52ac2115530027a5562abf20cf
Timestamp: 1694291881 Timestamp [UCT]: 2023-09-09 20:38:01 Age [y:d:h:m:s]: 01:013:02:52:28
Block: 844607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270664 RingCT/type: yes/0
Extra: 01ea53b294c80edc3e9dc91ceb4a2ada633962ea52ac2115530027a5562abf20cf02110000000433af99f4000000000000000000

1 output(s) for total of 0.976037403000 dcy

stealth address amount amount idx
00: 596866f4fbdcb08f2ebe852a7702d9f7026cf78e77f7f6281dfa9456fcc6ef53 0.976037403000 1297927 of 0

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": 844617, "vin": [ { "gen": { "height": 844607 } } ], "vout": [ { "amount": 976037403, "target": { "key": "596866f4fbdcb08f2ebe852a7702d9f7026cf78e77f7f6281dfa9456fcc6ef53" } } ], "extra": [ 1, 234, 83, 178, 148, 200, 14, 220, 62, 157, 201, 28, 235, 74, 42, 218, 99, 57, 98, 234, 82, 172, 33, 21, 83, 0, 39, 165, 86, 42, 191, 32, 207, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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