Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eb0b90c6425ca448216e2d26ba4e9b13d51e7f237c0b0594ebf713fb392ca42

Tx prefix hash: f9ca5f60ba2b78f8e5604794b15a50d656573a624f4bce01c990fcf45cb1fe54
Tx public key: fabe5d243741632cc46b93cdbda74a1bff96cf34031851ea392ed9fffc8dcc8c
Timestamp: 1715064757 Timestamp [UCT]: 2024-05-07 06:52:37 Age [y:d:h:m:s]: 00:239:07:03:17
Block: 1016644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171275 RingCT/type: yes/0
Extra: 01fabe5d243741632cc46b93cdbda74a1bff96cf34031851ea392ed9fffc8dcc8c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab0895be38c2f617a6a641b52637ac4ffc8d0e5e3b000d25f5b6db498073b242 0.600000000000 1480289 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": 1016654, "vin": [ { "gen": { "height": 1016644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab0895be38c2f617a6a641b52637ac4ffc8d0e5e3b000d25f5b6db498073b242" } } ], "extra": [ 1, 250, 190, 93, 36, 55, 65, 99, 44, 196, 107, 147, 205, 189, 167, 74, 27, 255, 150, 207, 52, 3, 24, 81, 234, 57, 46, 217, 255, 252, 141, 204, 140, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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