Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebc1a50246a26098fdc538f0643587d34bdc3b2e72ff952f3c352f68ca0d8435

Tx prefix hash: e9d737858b6750fe8190977bc758f51178f79687db53ca5e246a0f84bc1f4d1b
Tx public key: 2a5a05424ec1db449ff2a79c7953a45bcfbd8050dc1a75ca280308a7d1349b40
Timestamp: 1713826623 Timestamp [UCT]: 2024-04-22 22:57:03 Age [y:d:h:m:s]: 01:200:14:10:52
Block: 1006377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402003 RingCT/type: yes/0
Extra: 012a5a05424ec1db449ff2a79c7953a45bcfbd8050dc1a75ca280308a7d1349b400211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7055dd94ff7a4a2ea36f44f9cb03f9e25a0c4deb50b28394310bea11006ac8a6 0.600000000000 1467395 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": 1006387, "vin": [ { "gen": { "height": 1006377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7055dd94ff7a4a2ea36f44f9cb03f9e25a0c4deb50b28394310bea11006ac8a6" } } ], "extra": [ 1, 42, 90, 5, 66, 78, 193, 219, 68, 159, 242, 167, 156, 121, 83, 164, 91, 207, 189, 128, 80, 220, 26, 117, 202, 40, 3, 8, 167, 209, 52, 155, 64, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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