Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b87bd18d9694d5ee694e47b6fd95ecd4277741f06a0e488a07564a026a762007

Tx prefix hash: 85381db1dd599e6a7a36d4561357df0d467d467b23373ce3f3ccf47659e6a4cc
Tx public key: 139dde6ad1ecf06f3b3f551544b04f899858a2ade47533e3a0e1a5eeed2274d4
Timestamp: 1580701526 Timestamp [UCT]: 2020-02-03 03:45:26 Age [y:d:h:m:s]: 05:119:16:06:16
Block: 57656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1237469 RingCT/type: yes/0
Extra: 01139dde6ad1ecf06f3b3f551544b04f899858a2ade47533e3a0e1a5eeed2274d40211000000012264afe6000000000000000000

1 output(s) for total of 395.332537116000 dcy

stealth address amount amount idx
00: 509ef2b8aef8cc6e4563585ac3562172c3525c892234f1a9dcded0d1a252f967 395.332537116000 106560 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": 57666, "vin": [ { "gen": { "height": 57656 } } ], "vout": [ { "amount": 395332537116, "target": { "key": "509ef2b8aef8cc6e4563585ac3562172c3525c892234f1a9dcded0d1a252f967" } } ], "extra": [ 1, 19, 157, 222, 106, 209, 236, 240, 111, 59, 63, 85, 21, 68, 176, 79, 137, 152, 88, 162, 173, 228, 117, 51, 227, 160, 225, 165, 238, 237, 34, 116, 212, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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