Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5772f23f0363bd445c67d554249347aca4d2d4398a6a61ed123d517df3b719f6

Tx prefix hash: 58b7bb132e6add4cdade19bf96aa4b037b82f405626575da2d045baccd405e10
Tx public key: 67e5b3e9e26166ab7b5f17882d91d7622e7feaad500a5a4c1b2b89fbe14a3284
Timestamp: 1720416316 Timestamp [UCT]: 2024-07-08 05:25:16 Age [y:d:h:m:s]: 00:337:16:52:41
Block: 1061007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241344 RingCT/type: yes/0
Extra: 0167e5b3e9e26166ab7b5f17882d91d7622e7feaad500a5a4c1b2b89fbe14a3284021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e65c40cd1e280c9dc6575f8bad4d49c6af634d18686bb159bf559cafff29564 0.600000000000 1531498 of 15

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": 1061017, "vin": [ { "gen": { "height": 1061007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e65c40cd1e280c9dc6575f8bad4d49c6af634d18686bb159bf559cafff29564" } } ], "extra": [ 1, 103, 229, 179, 233, 226, 97, 102, 171, 123, 95, 23, 136, 45, 145, 215, 98, 46, 127, 234, 173, 80, 10, 90, 76, 27, 43, 137, 251, 225, 74, 50, 132, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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