Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9df6587629a32d03af5b97290566ea5c886771a96187806cb64c528603846e40

Tx prefix hash: 8282ea87df4d8dbdb4f1d36e72fad8aaff4ff912abe56d3e60db47979818309b
Tx public key: ed382806cf44f033320393789a4b57d8fbd4ea8b6f56841bffd9fb04e7fd2f4f
Timestamp: 1725508905 Timestamp [UCT]: 2024-09-05 04:01:45 Age [y:d:h:m:s]: 00:217:19:06:39
Block: 1103230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155501 RingCT/type: yes/0
Extra: 01ed382806cf44f033320393789a4b57d8fbd4ea8b6f56841bffd9fb04e7fd2f4f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e0a2e4d943e259d22ce4637ae8745fa4e844e1f9a4d57581e72d2e98abdb4c5 0.600000000000 1579977 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": 1103240, "vin": [ { "gen": { "height": 1103230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e0a2e4d943e259d22ce4637ae8745fa4e844e1f9a4d57581e72d2e98abdb4c5" } } ], "extra": [ 1, 237, 56, 40, 6, 207, 68, 240, 51, 50, 3, 147, 120, 154, 75, 87, 216, 251, 212, 234, 139, 111, 86, 132, 27, 255, 217, 251, 4, 231, 253, 47, 79, 2, 17, 0, 0, 0, 2, 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