Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1cb79948405f38c65407555c8139b7b3dc822ac5cace8fd21eedd4a246a5785

Tx prefix hash: ca923f9dddcc2f8fc28fb65bd893651770a8c7869f3f5030e641cb41264e77c5
Tx public key: 5cdfd7856496f85e9618e9e549496866a2d1776ac7be785bbe20efd4e1bea0f0
Timestamp: 1721612795 Timestamp [UCT]: 2024-07-22 01:46:35 Age [y:d:h:m:s]: 01:111:22:57:15
Block: 1070914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338532 RingCT/type: yes/0
Extra: 015cdfd7856496f85e9618e9e549496866a2d1776ac7be785bbe20efd4e1bea0f00211000000050cce0636000000000000000000

1 output(s) for total of 0.615580000000 dcy

stealth address amount amount idx
00: 03ba3e5a98640197c4de6cb5ee1e5a477a091ed52caa97c0060c7c663094c5e7 0.615580000000 1542941 of 0

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": 1070924, "vin": [ { "gen": { "height": 1070914 } } ], "vout": [ { "amount": 615580000, "target": { "key": "03ba3e5a98640197c4de6cb5ee1e5a477a091ed52caa97c0060c7c663094c5e7" } } ], "extra": [ 1, 92, 223, 215, 133, 100, 150, 248, 94, 150, 24, 233, 229, 73, 73, 104, 102, 162, 209, 119, 106, 199, 190, 120, 91, 190, 32, 239, 212, 225, 190, 160, 240, 2, 17, 0, 0, 0, 5, 12, 206, 6, 54, 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