Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80b9abbffa59d3c95ec1105c2e37aebf231ecdcad4663b5b1e6d660d3c1a147b

Tx prefix hash: ed3de8c941138b3ba346a28417aed570212ee9627f163f9ea800c820a0dc1ddb
Tx public key: 56666f8042f91a1f88af85383db3eda69a98e98c870abfa2bce7f7a4a0895c29
Timestamp: 1735428962 Timestamp [UCT]: 2024-12-28 23:36:02 Age [y:d:h:m:s]: 00:096:17:14:37
Block: 1185340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68914 RingCT/type: yes/0
Extra: 0156666f8042f91a1f88af85383db3eda69a98e98c870abfa2bce7f7a4a0895c290211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c183f8b28a8d5ccbc1825d8357ab1d2a2cc5e09e1ef6623244e1bc8195a8036e 0.600000000000 1671807 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": 1185350, "vin": [ { "gen": { "height": 1185340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c183f8b28a8d5ccbc1825d8357ab1d2a2cc5e09e1ef6623244e1bc8195a8036e" } } ], "extra": [ 1, 86, 102, 111, 128, 66, 249, 26, 31, 136, 175, 133, 56, 61, 179, 237, 166, 154, 152, 233, 140, 135, 10, 191, 162, 188, 231, 247, 164, 160, 137, 92, 41, 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