Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68fc8028eed35074bb9caac39b016d33543d12db70414527066f2f96d8d514f3

Tx prefix hash: 4a56f3fb5f9a814cd278792741254a403a456d0ea27c0b54167082457ca204b9
Tx public key: a51d27f7ea22277c6c91af555cfb10c02c8de5d2c163c642f1e486eb0a735db6
Timestamp: 1711471204 Timestamp [UCT]: 2024-03-26 16:40:04 Age [y:d:h:m:s]: 00:358:03:18:46
Block: 986871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256058 RingCT/type: yes/0
Extra: 01a51d27f7ea22277c6c91af555cfb10c02c8de5d2c163c642f1e486eb0a735db602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cdd3b489f18f86029b0ebfde4e74dbd8028ac0f2e72abcdb529e0d9d08d5c67 0.600000000000 1447106 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": 986881, "vin": [ { "gen": { "height": 986871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cdd3b489f18f86029b0ebfde4e74dbd8028ac0f2e72abcdb529e0d9d08d5c67" } } ], "extra": [ 1, 165, 29, 39, 247, 234, 34, 39, 124, 108, 145, 175, 85, 92, 251, 16, 192, 44, 141, 229, 210, 193, 99, 198, 66, 241, 228, 134, 235, 10, 115, 93, 182, 2, 17, 0, 0, 0, 2, 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