Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 834fc1b9ce25f7a97a53c7e3e4a2c3b5eed8daee19bcc36ac043bf74b87e41e9

Tx prefix hash: e8a9027c3fecd4fb3f7b2f9a2e93b88d8f2865b96d82b46a048a49b858687b31
Tx public key: 9145f97e1a2e85f49b942b80a27abb3e2af3753918331defad4cc5c4a8beaca8
Timestamp: 1745971529 Timestamp [UCT]: 2025-04-30 00:05:29 Age [y:d:h:m:s]: 00:018:23:01:07
Block: 1272357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13544 RingCT/type: yes/0
Extra: 019145f97e1a2e85f49b942b80a27abb3e2af3753918331defad4cc5c4a8beaca80211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a162abf583ef2c4a2187e9bdf0a0a3804e2adc0197f9e8e07c19b038bf9764f 0.600000000000 1759632 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": 1272367, "vin": [ { "gen": { "height": 1272357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a162abf583ef2c4a2187e9bdf0a0a3804e2adc0197f9e8e07c19b038bf9764f" } } ], "extra": [ 1, 145, 69, 249, 126, 26, 46, 133, 244, 155, 148, 43, 128, 162, 122, 187, 62, 42, 243, 117, 57, 24, 51, 29, 239, 173, 76, 197, 196, 168, 190, 172, 168, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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