Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ba36fc4daab6e0a9393e936eeafca0eb2a1236276fc51b55ca47fc90d6a0211

Tx prefix hash: 79412b21b807fb89c043de8c31a0152b5cba815f308aba5615a5ff90bf525ffa
Tx public key: ef81ee494afab6b0987af819c1fd6d110e755e33dcec8e9aafbd12cfc5306619
Timestamp: 1717609575 Timestamp [UCT]: 2024-06-05 17:46:15 Age [y:d:h:m:s]: 00:232:02:54:42
Block: 1037741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166063 RingCT/type: yes/0
Extra: 01ef81ee494afab6b0987af819c1fd6d110e755e33dcec8e9aafbd12cfc530661902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4361bde14f6e5bf592c07b65186ce463f78addc0e87aa038fb9a1a8d96e1ccc 0.600000000000 1506296 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": 1037751, "vin": [ { "gen": { "height": 1037741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4361bde14f6e5bf592c07b65186ce463f78addc0e87aa038fb9a1a8d96e1ccc" } } ], "extra": [ 1, 239, 129, 238, 73, 74, 250, 182, 176, 152, 122, 248, 25, 193, 253, 109, 17, 14, 117, 94, 51, 220, 236, 142, 154, 175, 189, 18, 207, 197, 48, 102, 25, 2, 17, 0, 0, 0, 1, 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