Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56917d1a3edf57e5bf3fc5e7b7a2dae1b3c4777d3b2831dce2f8f01e20eb73e7

Tx prefix hash: a7b785ff94170aad7287824275bc38356bbed218bba26bf3a6a413b3cbf9787a
Tx public key: 9b6627c9170fc6b039a3c1ff7247a6c35b3ffffe36440221b60068c5e93d702c
Timestamp: 1768226561 Timestamp [UCT]: 2026-01-12 14:02:41 Age [y:d:h:m:s]: 00:013:12:56:54
Block: 1454145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9601 RingCT/type: yes/0
Extra: 019b6627c9170fc6b039a3c1ff7247a6c35b3ffffe36440221b60068c5e93d702c02110000000a49d73e98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8636fa0296548cabd30221d80f737c0e3f24dcd03b7e24eb13bab1b7056d464 0.600000000000 1943231 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": 1454155, "vin": [ { "gen": { "height": 1454145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8636fa0296548cabd30221d80f737c0e3f24dcd03b7e24eb13bab1b7056d464" } } ], "extra": [ 1, 155, 102, 39, 201, 23, 15, 198, 176, 57, 163, 193, 255, 114, 71, 166, 195, 91, 63, 255, 254, 54, 68, 2, 33, 182, 0, 104, 197, 233, 61, 112, 44, 2, 17, 0, 0, 0, 10, 73, 215, 62, 152, 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