Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfab641ef7bb17f50a41d1a25fb5088e908d221ac40e7f708c772733682abc35

Tx prefix hash: eeca058552bb4429b1413d9dc7d6233eec9e66d8f488b99be4eb5d45621c9e9e
Tx public key: 50b7096e0e262029b3af713826e0803aaf4d36484578c87233af19c2734a4d67
Timestamp: 1638759273 Timestamp [UCT]: 2021-12-06 02:54:33 Age [y:d:h:m:s]: 02:361:07:54:56
Block: 389369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776287 RingCT/type: yes/0
Extra: 0150b7096e0e262029b3af713826e0803aaf4d36484578c87233af19c2734a4d67021100000001e9564d6f000000000000000000

1 output(s) for total of 31.467282223000 dcy

stealth address amount amount idx
00: 0f796e67fad634f0fb40f1ab2e4ca14fdfffcc6b3f4aa250665d67834ce75f27 31.467282223000 784496 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": 389379, "vin": [ { "gen": { "height": 389369 } } ], "vout": [ { "amount": 31467282223, "target": { "key": "0f796e67fad634f0fb40f1ab2e4ca14fdfffcc6b3f4aa250665d67834ce75f27" } } ], "extra": [ 1, 80, 183, 9, 110, 14, 38, 32, 41, 179, 175, 113, 56, 38, 224, 128, 58, 175, 77, 54, 72, 69, 120, 200, 114, 51, 175, 25, 194, 115, 74, 77, 103, 2, 17, 0, 0, 0, 1, 233, 86, 77, 111, 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