Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf9f4705f1ad0164bc9c86c75a4334095ec6e1e37ab03f45678d4ce20864555

Tx prefix hash: e86127128b506e0fd8ea3f3452ec44bd4b481ecc2ea828064e20f195fab2f5bc
Tx public key: c5cb5c90a8290b15a53dfe394d85a961bacaa0cd5b8f7ce31410e5bd9fef0907
Timestamp: 1728976617 Timestamp [UCT]: 2024-10-15 07:16:57 Age [y:d:h:m:s]: 00:193:04:55:41
Block: 1131978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137885 RingCT/type: yes/0
Extra: 01c5cb5c90a8290b15a53dfe394d85a961bacaa0cd5b8f7ce31410e5bd9fef0907021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6667469c0b485fe98838a2cbaecd6036b2b1c163030e0b0ebad48194c7e2f873 0.600000000000 1614887 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": 1131988, "vin": [ { "gen": { "height": 1131978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6667469c0b485fe98838a2cbaecd6036b2b1c163030e0b0ebad48194c7e2f873" } } ], "extra": [ 1, 197, 203, 92, 144, 168, 41, 11, 21, 165, 61, 254, 57, 77, 133, 169, 97, 186, 202, 160, 205, 91, 143, 124, 227, 20, 16, 229, 189, 159, 239, 9, 7, 2, 17, 0, 0, 0, 3, 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