Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef9e010086392edd3b861879a793143464284a92576ed795260cd89908a6cfc7

Tx prefix hash: 3a3e79f35a1f4c8c4f2047f91b05c482c35d311737d47f91b14a4537ee4667e5
Tx public key: 19b2d381190aebb52cc2e3edbc5640b914adabf1fca0f8c90d97fa9b2f6f995e
Timestamp: 1578908752 Timestamp [UCT]: 2020-01-13 09:45:52 Age [y:d:h:m:s]: 05:080:04:44:12
Block: 44470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207563 RingCT/type: yes/0
Extra: 0119b2d381190aebb52cc2e3edbc5640b914adabf1fca0f8c90d97fa9b2f6f995e02110000000149b77a3d000000000000000000

1 output(s) for total of 437.172938419000 dcy

stealth address amount amount idx
00: c5430a6c43b45c9a88b9d8d9239fb9778dc8f7a88b46798aa05e2ab3cc15b094 437.172938419000 80930 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": 44480, "vin": [ { "gen": { "height": 44470 } } ], "vout": [ { "amount": 437172938419, "target": { "key": "c5430a6c43b45c9a88b9d8d9239fb9778dc8f7a88b46798aa05e2ab3cc15b094" } } ], "extra": [ 1, 25, 178, 211, 129, 25, 10, 235, 181, 44, 194, 227, 237, 188, 86, 64, 185, 20, 173, 171, 241, 252, 160, 248, 201, 13, 151, 250, 155, 47, 111, 153, 94, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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