Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a83448d7d22f14f7689d1d35a4835adaad13abd28b2d66139f281c30fc01df8f

Tx prefix hash: b4820a5894ae66a188de421f203f6a174dbe405bf677aea63411a22a6b308c85
Tx public key: 51f37cedb895b5b59ba438e58e88f5be1417f8b8a1096d35626fe4f759b10e40
Timestamp: 1730310202 Timestamp [UCT]: 2024-10-30 17:43:22 Age [y:d:h:m:s]: 00:160:05:25:03
Block: 1142954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114341 RingCT/type: yes/0
Extra: 0151f37cedb895b5b59ba438e58e88f5be1417f8b8a1096d35626fe4f759b10e4002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83957a11a48e4b5b1f4e76a4007a31c51d8f7f00f03054a6abfcf15b2dafc92c 0.600000000000 1626811 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": 1142964, "vin": [ { "gen": { "height": 1142954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83957a11a48e4b5b1f4e76a4007a31c51d8f7f00f03054a6abfcf15b2dafc92c" } } ], "extra": [ 1, 81, 243, 124, 237, 184, 149, 181, 181, 155, 164, 56, 229, 142, 136, 245, 190, 20, 23, 248, 184, 161, 9, 109, 53, 98, 111, 228, 247, 89, 177, 14, 64, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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