Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34638729bda792d877522f4085a8f8aebcd4ce16e7b3b01098e0110239a07b1

Tx prefix hash: fbccf5f17d9197f747a0e32b2d0d02c2346ad6e230cd2fdad6c3b03221a849b9
Tx public key: df23c60fe9b88dcbf8fb2e2c88e49f23b1de92a60612ceae71e6fe086f193cc1
Timestamp: 1672737897 Timestamp [UCT]: 2023-01-03 09:24:57 Age [y:d:h:m:s]: 02:142:23:48:07
Block: 666595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623927 RingCT/type: yes/0
Extra: 01df23c60fe9b88dcbf8fb2e2c88e49f23b1de92a60612ceae71e6fe086f193cc1021100000009e6d27f9c000000000000000000

1 output(s) for total of 3.795718621000 dcy

stealth address amount amount idx
00: 0eb74ef9e81f88dc75c47e147e9f62cc964e73a5ac770d50c1509825ab1caf74 3.795718621000 1107722 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": 666605, "vin": [ { "gen": { "height": 666595 } } ], "vout": [ { "amount": 3795718621, "target": { "key": "0eb74ef9e81f88dc75c47e147e9f62cc964e73a5ac770d50c1509825ab1caf74" } } ], "extra": [ 1, 223, 35, 198, 15, 233, 184, 141, 203, 248, 251, 46, 44, 136, 228, 159, 35, 177, 222, 146, 166, 6, 18, 206, 174, 113, 230, 254, 8, 111, 25, 60, 193, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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