Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d40d775ca77794205fef9283f16f3e26c10c95a05448ed8534565b367497c32

Tx prefix hash: 0a3400487d555019e6a93b5f7d984cb5064f9ee98a00507fb5f83c6e1649d169
Tx public key: 8e1d3f968787b55986d4919c8950c5b26a93c58aa1f1cfadec5786ae80a013c3
Timestamp: 1750664291 Timestamp [UCT]: 2025-06-23 07:38:11 Age [y:d:h:m:s]: 00:140:08:30:49
Block: 1311000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98197 RingCT/type: yes/0
Extra: 018e1d3f968787b55986d4919c8950c5b26a93c58aa1f1cfadec5786ae80a013c30211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21824b9ca8d4b52843dbae96d636e3c7d8b03e75a64757962369b59672780f3c 0.600000000000 1798625 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": 1311010, "vin": [ { "gen": { "height": 1311000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21824b9ca8d4b52843dbae96d636e3c7d8b03e75a64757962369b59672780f3c" } } ], "extra": [ 1, 142, 29, 63, 150, 135, 135, 181, 89, 134, 212, 145, 156, 137, 80, 197, 178, 106, 147, 197, 138, 161, 241, 207, 173, 236, 87, 134, 174, 128, 160, 19, 195, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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