Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d80ee21aa00c73c441511ec4df86b40a618de1bef5682375544784a0126341c

Tx prefix hash: 50b8ad7f335e2ce33bc38070f72ef27aaf0cedfdba120c4e2cd270a57849895f
Tx public key: 32800e2f778f8d69e6a5f63e67ae36dba2cdd5e93eb83b0ffac8b2ae51cb0d2e
Timestamp: 1737347485 Timestamp [UCT]: 2025-01-20 04:31:25 Age [y:d:h:m:s]: 00:149:08:00:29
Block: 1201180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106477 RingCT/type: yes/0
Extra: 0132800e2f778f8d69e6a5f63e67ae36dba2cdd5e93eb83b0ffac8b2ae51cb0d2e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 491306e7c968c175e65874f78d25d695aaa3c3562c33b3f52ada88ddd279cedf 0.600000000000 1687829 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": 1201190, "vin": [ { "gen": { "height": 1201180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "491306e7c968c175e65874f78d25d695aaa3c3562c33b3f52ada88ddd279cedf" } } ], "extra": [ 1, 50, 128, 14, 47, 119, 143, 141, 105, 230, 165, 246, 62, 103, 174, 54, 219, 162, 205, 213, 233, 62, 184, 59, 15, 250, 200, 178, 174, 81, 203, 13, 46, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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