Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc0930e8b5c34d400e4c76471feb196ac167472848aaf91f48e11e0efd264ff

Tx prefix hash: 973108b200e40ccb1572fd68ecb6772846a9aeada0f93d14ae26e82b94a2a1f7
Tx public key: 772b3916d889ec773d827ce72182b662bcd605aa15187de1b5e017e0e743591b
Timestamp: 1633352770 Timestamp [UCT]: 2021-10-04 13:06:10 Age [y:d:h:m:s]: 02:353:00:41:37
Block: 346505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 768476 RingCT/type: yes/0
Extra: 01772b3916d889ec773d827ce72182b662bcd605aa15187de1b5e017e0e743591b02110000000c3fc41461000000000000000000

1 output(s) for total of 43.640078386000 dcy

stealth address amount amount idx
00: ec778ae97b6aff25685509c31e3e8cc4c80f347a898d9ec9d656a3f0cbafd382 43.640078386000 710441 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": 346515, "vin": [ { "gen": { "height": 346505 } } ], "vout": [ { "amount": 43640078386, "target": { "key": "ec778ae97b6aff25685509c31e3e8cc4c80f347a898d9ec9d656a3f0cbafd382" } } ], "extra": [ 1, 119, 43, 57, 22, 216, 137, 236, 119, 61, 130, 124, 231, 33, 130, 182, 98, 188, 214, 5, 170, 21, 24, 125, 225, 181, 224, 23, 224, 231, 67, 89, 27, 2, 17, 0, 0, 0, 12, 63, 196, 20, 97, 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