Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f6db1745720c85dbc2353c985b8d670722c1cb810ec27eaf5955e7d05fdf7a8

Tx prefix hash: a9385310dd098f87eeed835e1e02e050acef4f542d8460e3015562e6681acd97
Tx public key: 403f7fbe49338c6bdc24787a13b5f9ae6a7d80486e201f8a0ddb184057242579
Timestamp: 1716723440 Timestamp [UCT]: 2024-05-26 11:37:20 Age [y:d:h:m:s]: 00:314:02:41:04
Block: 1030401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224488 RingCT/type: yes/0
Extra: 01403f7fbe49338c6bdc24787a13b5f9ae6a7d80486e201f8a0ddb1840572425790211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ec3b8e005bccc541f59170f6ea1dcaeaf2d54ca80e0c6482f128790a71a0a9c 0.600000000000 1498656 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": 1030411, "vin": [ { "gen": { "height": 1030401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ec3b8e005bccc541f59170f6ea1dcaeaf2d54ca80e0c6482f128790a71a0a9c" } } ], "extra": [ 1, 64, 63, 127, 190, 73, 51, 140, 107, 220, 36, 120, 122, 19, 181, 249, 174, 106, 125, 128, 72, 110, 32, 31, 138, 13, 219, 24, 64, 87, 36, 37, 121, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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