Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 254a6222c6fa6d3724cc47b3c62ce082aa3394974fd7afa3b880f7d5eb269da8

Tx prefix hash: 220a5cffc2fe82a42f6e94028c792c8466d4bf905492ce0f1d2cba1a163eec03
Tx public key: b488cdd40455101cab35b05c44450831d3cd8e1e6933e3ddb667f5a65bdcf61e
Timestamp: 1705556142 Timestamp [UCT]: 2024-01-18 05:35:42 Age [y:d:h:m:s]: 01:295:21:20:54
Block: 937780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470292 RingCT/type: yes/0
Extra: 01b488cdd40455101cab35b05c44450831d3cd8e1e6933e3ddb667f5a65bdcf61e02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b49ca8ce761f6df0a4ae7b223242d9211b436d864954c2be22a4ceb1c20b71c7 0.600000000000 1395844 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": 937790, "vin": [ { "gen": { "height": 937780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b49ca8ce761f6df0a4ae7b223242d9211b436d864954c2be22a4ceb1c20b71c7" } } ], "extra": [ 1, 180, 136, 205, 212, 4, 85, 16, 28, 171, 53, 176, 92, 68, 69, 8, 49, 211, 205, 142, 30, 105, 51, 227, 221, 182, 103, 245, 166, 91, 220, 246, 30, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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