Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12bb9c26d14fa891a001edde3f69e0b988f56d70622ce6fc73638d7915b09689

Tx prefix hash: 357e8b64dc1587e638dd1221d0bdf34a535e1f0b364b295e30aa3ff69ad83539
Tx public key: 3245f3dfcee3fffcb92d94c707e8c9048309c33a36dca93808102f9e722ee59e
Timestamp: 1612784615 Timestamp [UCT]: 2021-02-08 11:43:35 Age [y:d:h:m:s]: 03:362:16:03:40
Block: 194508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1017871 RingCT/type: yes/0
Extra: 013245f3dfcee3fffcb92d94c707e8c9048309c33a36dca93808102f9e722ee59e02110000045ec6b81c9d000000000000000000

1 output(s) for total of 139.164958276000 dcy

stealth address amount amount idx
00: 166cbd7eb98c7a905cfee6583d54ef29276012a857d0b5113341de8044c3284d 139.164958276000 394962 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": 194518, "vin": [ { "gen": { "height": 194508 } } ], "vout": [ { "amount": 139164958276, "target": { "key": "166cbd7eb98c7a905cfee6583d54ef29276012a857d0b5113341de8044c3284d" } } ], "extra": [ 1, 50, 69, 243, 223, 206, 227, 255, 252, 185, 45, 148, 199, 7, 232, 201, 4, 131, 9, 195, 58, 54, 220, 169, 56, 8, 16, 47, 158, 114, 46, 229, 158, 2, 17, 0, 0, 4, 94, 198, 184, 28, 157, 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