Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41720f2c4cfe4b985a2638b48e4c52242ab661d58696c42e836b7e1863aa5b55

Tx prefix hash: 9c20e708a3a32e7434c8a1f5d569ae86ded815beff7d77d457c9b2c85baa1c53
Tx public key: ab00443c3628bae03dbee525fbd760acbd4406ba3f36c0fc6b61be5eea295380
Timestamp: 1634760495 Timestamp [UCT]: 2021-10-20 20:08:15 Age [y:d:h:m:s]: 03:019:07:29:05
Block: 356977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 791999 RingCT/type: yes/0
Extra: 01ab00443c3628bae03dbee525fbd760acbd4406ba3f36c0fc6b61be5eea295380021100000002f4c548b5000000000000000000

1 output(s) for total of 40.289786843000 dcy

stealth address amount amount idx
00: 8cd2801a098775f96a5743173f6a43f1ac305c5de63cac963821f5d093d8f944 40.289786843000 728105 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": 356987, "vin": [ { "gen": { "height": 356977 } } ], "vout": [ { "amount": 40289786843, "target": { "key": "8cd2801a098775f96a5743173f6a43f1ac305c5de63cac963821f5d093d8f944" } } ], "extra": [ 1, 171, 0, 68, 60, 54, 40, 186, 224, 61, 190, 229, 37, 251, 215, 96, 172, 189, 68, 6, 186, 63, 54, 192, 252, 107, 97, 190, 94, 234, 41, 83, 128, 2, 17, 0, 0, 0, 2, 244, 197, 72, 181, 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