Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0918e0bba4ad0fad7affa0e3adedf4837a188f6e3cb01df42dbf8f197c23dcca

Tx prefix hash: e502b54602a8a4d40db41e9dd1674c710cb2fbf1b9da8aa37adb9d214ef4e406
Tx public key: 03254290e57745ac59f1fe4c7b0422f098d03abb464774ae816797c331438393
Timestamp: 1760015052 Timestamp [UCT]: 2025-10-09 13:04:12 Age [y:d:h:m:s]: 00:031:15:08:01
Block: 1386177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22657 RingCT/type: yes/0
Extra: 0103254290e57745ac59f1fe4c7b0422f098d03abb464774ae816797c331438393021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d46a1504ff21c1318d215e3eefe720df8ee8c3ace0b4f34ec2b1a9ce0f7c9ec 0.600000000000 1874342 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": 1386187, "vin": [ { "gen": { "height": 1386177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d46a1504ff21c1318d215e3eefe720df8ee8c3ace0b4f34ec2b1a9ce0f7c9ec" } } ], "extra": [ 1, 3, 37, 66, 144, 229, 119, 69, 172, 89, 241, 254, 76, 123, 4, 34, 240, 152, 208, 58, 187, 70, 71, 116, 174, 129, 103, 151, 195, 49, 67, 131, 147, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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