Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7a1441db2c4a01473ba4b791d13c57e1811c7419603d38606e9c71e51833aaa

Tx prefix hash: cb8deec50d1a8994a2212e7dc8fdb4da91b3e06dd5440ae4d8abbb0faba88b4f
Tx public key: 9caee4b4033803d7f87e41c3b063bc4291595e9abdbb53db6f76215b7daceda3
Timestamp: 1703051776 Timestamp [UCT]: 2023-12-20 05:56:16 Age [y:d:h:m:s]: 01:021:22:09:21
Block: 917047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277010 RingCT/type: yes/0
Extra: 019caee4b4033803d7f87e41c3b063bc4291595e9abdbb53db6f76215b7daceda3021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d90b8bb9c40afde03466bbdb656ae94b931732452770fa112b7644b41cfd68cf 0.600000000000 1374611 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": 917057, "vin": [ { "gen": { "height": 917047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d90b8bb9c40afde03466bbdb656ae94b931732452770fa112b7644b41cfd68cf" } } ], "extra": [ 1, 156, 174, 228, 180, 3, 56, 3, 215, 248, 126, 65, 195, 176, 99, 188, 66, 145, 89, 94, 154, 189, 187, 83, 219, 111, 118, 33, 91, 125, 172, 237, 163, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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