Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc9bd423f654cef5259ac675b794d9193d9fd48de85645e863bf01a34ca2250d

Tx prefix hash: 33974c69b1c52c68a780f99f25e3e63669c504364a716e1ed92a2947eebc5735
Tx public key: 71e9af7ecee6238f6cfcceb0bc7d2b2204fd11600fd50a42dc4d740a994c043e
Timestamp: 1735085864 Timestamp [UCT]: 2024-12-25 00:17:44 Age [y:d:h:m:s]: 00:096:22:04:46
Block: 1182504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69049 RingCT/type: yes/0
Extra: 0171e9af7ecee6238f6cfcceb0bc7d2b2204fd11600fd50a42dc4d740a994c043e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61137183a0e8a26ea38f818b56f08c120d4fab279378d28e4db070232bc7dd80 0.600000000000 1668939 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": 1182514, "vin": [ { "gen": { "height": 1182504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61137183a0e8a26ea38f818b56f08c120d4fab279378d28e4db070232bc7dd80" } } ], "extra": [ 1, 113, 233, 175, 126, 206, 230, 35, 143, 108, 252, 206, 176, 188, 125, 43, 34, 4, 253, 17, 96, 15, 213, 10, 66, 220, 77, 116, 10, 153, 76, 4, 62, 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