Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 743526176ee0d5aa2f6dea6614d3b2f09b4124f84292521bb8e10e446e48e85b

Tx prefix hash: cabacb8316c0c8cdc3f06987e9f3dac832f69e4a4f9add79f7e0e3a7af7274f7
Tx public key: 0f836124c97dbf392c289a82a83ade017040fd90cba1ebb6ab8a90d7f217c31a
Timestamp: 1720485285 Timestamp [UCT]: 2024-07-09 00:34:45 Age [y:d:h:m:s]: 00:272:12:53:22
Block: 1061585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194703 RingCT/type: yes/0
Extra: 010f836124c97dbf392c289a82a83ade017040fd90cba1ebb6ab8a90d7f217c31a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8efd7c6c116b658402fbe94686678c9f3f73c997feef75ebd0eefe62bff53907 0.600000000000 1532076 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": 1061595, "vin": [ { "gen": { "height": 1061585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8efd7c6c116b658402fbe94686678c9f3f73c997feef75ebd0eefe62bff53907" } } ], "extra": [ 1, 15, 131, 97, 36, 201, 125, 191, 57, 44, 40, 154, 130, 168, 58, 222, 1, 112, 64, 253, 144, 203, 161, 235, 182, 171, 138, 144, 215, 242, 23, 195, 26, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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