Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 755b69c53b50d161c5acd2fa2b69d1c7689ee001b7e0d6cff7fce62ece4a542d

Tx prefix hash: bcd61b7c8c691cc480ba220e16e35fefcee87abf3d8dc51e3543c734387a41ef
Tx public key: 4f58ab5965d2a0e671be00604cf1fc48d85b7284bbb76cd883e06fb7145451d6
Timestamp: 1702025190 Timestamp [UCT]: 2023-12-08 08:46:30 Age [y:d:h:m:s]: 01:102:02:53:21
Block: 908535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334141 RingCT/type: yes/0
Extra: 014f58ab5965d2a0e671be00604cf1fc48d85b7284bbb76cd883e06fb7145451d6021100000008faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9629765e9c73c97d4dc394a0b53f820f52211e41839ba852fa86f77c6d696add 0.600000000000 1365568 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": 908545, "vin": [ { "gen": { "height": 908535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9629765e9c73c97d4dc394a0b53f820f52211e41839ba852fa86f77c6d696add" } } ], "extra": [ 1, 79, 88, 171, 89, 101, 210, 160, 230, 113, 190, 0, 96, 76, 241, 252, 72, 216, 91, 114, 132, 187, 183, 108, 216, 131, 224, 111, 183, 20, 84, 81, 214, 2, 17, 0, 0, 0, 8, 250, 243, 92, 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