Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 411ab1a1e4db496100e0b1cd34997445e92cc429f0c0368cde095ba4c4a2937a

Tx prefix hash: 1a8fb062077d010d62d25d6879c4e6c25ccbe30b8d6daadbd4a91248fc35c72f
Tx public key: 7f1f5fbee574540be635196354b15183a30064235231a3f5f46d12f5c9773c65
Timestamp: 1702320020 Timestamp [UCT]: 2023-12-11 18:40:20 Age [y:d:h:m:s]: 01:192:02:17:46
Block: 910983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398315 RingCT/type: yes/0
Extra: 017f1f5fbee574540be635196354b15183a30064235231a3f5f46d12f5c9773c6502110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d2e2c683076af7ac1f4bc00e82988e2413363ebea44f3c34ae970398a93a0d5 0.600000000000 1368158 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": 910993, "vin": [ { "gen": { "height": 910983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d2e2c683076af7ac1f4bc00e82988e2413363ebea44f3c34ae970398a93a0d5" } } ], "extra": [ 1, 127, 31, 95, 190, 229, 116, 84, 11, 230, 53, 25, 99, 84, 177, 81, 131, 163, 0, 100, 35, 82, 49, 163, 245, 244, 109, 18, 245, 201, 119, 60, 101, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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