Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be964d9567569d2743289d185b16b0e64438afeb5faafa04e573efed86980732

Tx prefix hash: 396c3ee9dec72a90ca5386b8e3c5213c7be4939b8c10f4cfc97c5726b14404da
Tx public key: 3e8135ece66a214e7e0053dbdd1dc1fb9f2ef87d25e191030f1c986879eebb3f
Timestamp: 1731723256 Timestamp [UCT]: 2024-11-16 02:14:16 Age [y:d:h:m:s]: 00:133:05:07:22
Block: 1154660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95016 RingCT/type: yes/0
Extra: 013e8135ece66a214e7e0053dbdd1dc1fb9f2ef87d25e191030f1c986879eebb3f0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a91c4a8c14683dc8c07d8fa41dde697b6cbaf39b6caeaca876cc4b2e1c5062d6 0.600000000000 1640273 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": 1154670, "vin": [ { "gen": { "height": 1154660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a91c4a8c14683dc8c07d8fa41dde697b6cbaf39b6caeaca876cc4b2e1c5062d6" } } ], "extra": [ 1, 62, 129, 53, 236, 230, 106, 33, 78, 126, 0, 83, 219, 221, 29, 193, 251, 159, 46, 248, 125, 37, 225, 145, 3, 15, 28, 152, 104, 121, 238, 187, 63, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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