Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27ebc6aa0979dcd9c732ad40c06cc43027a34d8e8011ed46c9891027c34d21e6

Tx prefix hash: 5ff1fe8da32f0388d78ceb30843f5a3f297acdc2263ebe8afdd05072fcd87ebc
Tx public key: 5304b9a32b3231a2b8d3db879c45080d58ffbea83901c9a1a684dc2e87edaf08
Timestamp: 1721979743 Timestamp [UCT]: 2024-07-26 07:42:23 Age [y:d:h:m:s]: 00:324:05:02:35
Block: 1073964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231574 RingCT/type: yes/0
Extra: 015304b9a32b3231a2b8d3db879c45080d58ffbea83901c9a1a684dc2e87edaf08021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a742e249a2fb69e9ed363c725bb79eaccff9599b4521c7c8afc5f3afc387f83 0.600000000000 1546473 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": 1073974, "vin": [ { "gen": { "height": 1073964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a742e249a2fb69e9ed363c725bb79eaccff9599b4521c7c8afc5f3afc387f83" } } ], "extra": [ 1, 83, 4, 185, 163, 43, 50, 49, 162, 184, 211, 219, 135, 156, 69, 8, 13, 88, 255, 190, 168, 57, 1, 201, 161, 166, 132, 220, 46, 135, 237, 175, 8, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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