Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 078b87c9f97f031188aeced9169bfe9d543f6d304d9df8cd51910535cd6a3684

Tx prefix hash: 482eb7f23d7863e7c1de2e5c224f69952a29f67270f3279b2773f8ca4e1b3f84
Tx public key: 40ef9674ee35eb3cc107c6ef922210d29ea9bb7b7d6240e09be1cc70f4abccd9
Timestamp: 1709425633 Timestamp [UCT]: 2024-03-03 00:27:13 Age [y:d:h:m:s]: 00:267:06:28:05
Block: 969891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191339 RingCT/type: yes/0
Extra: 0140ef9674ee35eb3cc107c6ef922210d29ea9bb7b7d6240e09be1cc70f4abccd902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 623040b930b094fb0988fffc849a244c69a5b3a44e2c015331fc842f18f100cd 0.600000000000 1429740 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": 969901, "vin": [ { "gen": { "height": 969891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "623040b930b094fb0988fffc849a244c69a5b3a44e2c015331fc842f18f100cd" } } ], "extra": [ 1, 64, 239, 150, 116, 238, 53, 235, 60, 193, 7, 198, 239, 146, 34, 16, 210, 158, 169, 187, 123, 125, 98, 64, 224, 155, 225, 204, 112, 244, 171, 204, 217, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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