Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c4df5e077291864733486c732e99551ac3e8f3a20d4b3a3926def2f7c423e4c

Tx prefix hash: 64920efd7b76bec5dd3a26c5e4c950a20fdc121ac0a6aaeb3bdca029b8ac8dbe
Tx public key: 918890c9bea043969ed92c79f8e9c3154ce2cf5df4dc93a63123c7ac001637ef
Timestamp: 1580953689 Timestamp [UCT]: 2020-02-06 01:48:09 Age [y:d:h:m:s]: 05:004:13:07:34
Block: 59400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155463 RingCT/type: yes/0
Extra: 01918890c9bea043969ed92c79f8e9c3154ce2cf5df4dc93a63123c7ac001637ef02110000000d8a2ee0d9000000000000000000

1 output(s) for total of 390.107195662000 dcy

stealth address amount amount idx
00: ff57074823b0fe45ba80e57c2d81c2c3d1ac3cdc8d2248c83f3f518a6535aa42 390.107195662000 109732 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": 59410, "vin": [ { "gen": { "height": 59400 } } ], "vout": [ { "amount": 390107195662, "target": { "key": "ff57074823b0fe45ba80e57c2d81c2c3d1ac3cdc8d2248c83f3f518a6535aa42" } } ], "extra": [ 1, 145, 136, 144, 201, 190, 160, 67, 150, 158, 217, 44, 121, 248, 233, 195, 21, 76, 226, 207, 93, 244, 220, 147, 166, 49, 35, 199, 172, 0, 22, 55, 239, 2, 17, 0, 0, 0, 13, 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