Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6534bfa44cb859907a92b8d843299670b8a043fe67c13fd1f4f5db625523dce

Tx prefix hash: 29d0c1658cc2bffa7262e127982a783ac0a1ac14b7aef9ac2a86f9aebd84ee5c
Tx public key: b951ff2e31b20551f2743e1a512950850444c0351e1b61a80cb5f2cf292909c8
Timestamp: 1682568958 Timestamp [UCT]: 2023-04-27 04:15:58 Age [y:d:h:m:s]: 01:276:08:21:53
Block: 747484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458756 RingCT/type: yes/0
Extra: 01b951ff2e31b20551f2743e1a512950850444c0351e1b61a80cb5f2cf292909c80211000000017e406890000000000000000000

1 output(s) for total of 2.047742856000 dcy

stealth address amount amount idx
00: 5cc6808927d1208b9ead47f829d4732b24533d4fe7c05eb60091601cf74adaf2 2.047742856000 1195159 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": 747494, "vin": [ { "gen": { "height": 747484 } } ], "vout": [ { "amount": 2047742856, "target": { "key": "5cc6808927d1208b9ead47f829d4732b24533d4fe7c05eb60091601cf74adaf2" } } ], "extra": [ 1, 185, 81, 255, 46, 49, 178, 5, 81, 242, 116, 62, 26, 81, 41, 80, 133, 4, 68, 192, 53, 30, 27, 97, 168, 12, 181, 242, 207, 41, 41, 9, 200, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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