Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d9db67f9ad5219c0b0cad429fb9a777ca79fab236b67edc3a4bdca0fbcfeea5

Tx prefix hash: 8fd618632d1a58348be9832e93092b6992945e9a0e702bbd10236271eeb2822a
Tx public key: bda615dea3787b6f6db2c01254fb645cba0e3ac69aea75672d03778474be620e
Timestamp: 1745762206 Timestamp [UCT]: 2025-04-27 13:56:46 Age [y:d:h:m:s]: 00:206:01:35:28
Block: 1270629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144980 RingCT/type: yes/0
Extra: 01bda615dea3787b6f6db2c01254fb645cba0e3ac69aea75672d03778474be620e0211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fef2c90cdc9a0e1b53af68ad1666bd11ff65d75f9184ec653a17e58314786af4 0.600000000000 1757872 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": 1270639, "vin": [ { "gen": { "height": 1270629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fef2c90cdc9a0e1b53af68ad1666bd11ff65d75f9184ec653a17e58314786af4" } } ], "extra": [ 1, 189, 166, 21, 222, 163, 120, 123, 111, 109, 178, 192, 18, 84, 251, 100, 92, 186, 14, 58, 198, 154, 234, 117, 103, 45, 3, 119, 132, 116, 190, 98, 14, 2, 17, 0, 0, 0, 6, 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