Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44a8bec3b8b8af161cc826be49bb1a4511c91974ed75ec423b1bcc3417b8cf6

Tx prefix hash: cb131434794b238bee605a35c4c0cf2e8ee164d3b5ab864fda0887f4d813c3a5
Tx public key: 471d0c2e7a42a31d350285c0dc6db8d1e7b8615eb5cf923e0c70fd8542f0b055
Timestamp: 1722516181 Timestamp [UCT]: 2024-08-01 12:43:01 Age [y:d:h:m:s]: 00:207:05:17:24
Block: 1078414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147968 RingCT/type: yes/0
Extra: 01471d0c2e7a42a31d350285c0dc6db8d1e7b8615eb5cf923e0c70fd8542f0b055021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e1351c6d798e69a0731efdb6fb478dae13d2c4db6fdd71297d76b546dc939b5 0.600000000000 1550991 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": 1078424, "vin": [ { "gen": { "height": 1078414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e1351c6d798e69a0731efdb6fb478dae13d2c4db6fdd71297d76b546dc939b5" } } ], "extra": [ 1, 71, 29, 12, 46, 122, 66, 163, 29, 53, 2, 133, 192, 220, 109, 184, 209, 231, 184, 97, 94, 181, 207, 146, 62, 12, 112, 253, 133, 66, 240, 176, 85, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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