Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 502115ce6d97483dbce4b49fbc1373be7017238ad4e4e056ea9113f10270817b

Tx prefix hash: 2924e84a11ef3388a95caa6ce7854a60c72a7b7ae3637b4b076562700c1b8c1c
Tx public key: 3bf7217349018f29d8fb461421831fd640bafd83f5e441a60a77cfec9231794b
Timestamp: 1576926687 Timestamp [UCT]: 2019-12-21 11:11:27 Age [y:d:h:m:s]: 04:345:12:09:23
Block: 28864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135726 RingCT/type: yes/0
Extra: 013bf7217349018f29d8fb461421831fd640bafd83f5e441a60a77cfec9231794b0211000000098a2ee0d9000000000000000000

1 output(s) for total of 492.450349411000 dcy

stealth address amount amount idx
00: f94936e2661089a5842bfbea7c0b7db701f47f3e14a2a4bc193f8ecb90f1f8c1 492.450349411000 47678 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": 28874, "vin": [ { "gen": { "height": 28864 } } ], "vout": [ { "amount": 492450349411, "target": { "key": "f94936e2661089a5842bfbea7c0b7db701f47f3e14a2a4bc193f8ecb90f1f8c1" } } ], "extra": [ 1, 59, 247, 33, 115, 73, 1, 143, 41, 216, 251, 70, 20, 33, 131, 31, 214, 64, 186, 253, 131, 245, 228, 65, 166, 10, 119, 207, 236, 146, 49, 121, 75, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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