Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00b269deb0daf00594f96820724a07f489a8a9f2fdc68e4c98d19c1b22de0738

Tx prefix hash: 841df33a77d6921458df455e430ec28a6216d7d0882efe6a5edfb0eeec85f7c2
Tx public key: 081ae7e354f2129b18334760d23fe94e6922ea8a39fff4d68b39846b38062a1b
Timestamp: 1750768608 Timestamp [UCT]: 2025-06-24 12:36:48 Age [y:d:h:m:s]: 00:181:08:04:47
Block: 1311813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127583 RingCT/type: yes/0
Extra: 01081ae7e354f2129b18334760d23fe94e6922ea8a39fff4d68b39846b38062a1b0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee6dd40c7b756b986fca10942c9924369622fd08f87379ea3ddff81314341189 0.600000000000 1799442 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": 1311823, "vin": [ { "gen": { "height": 1311813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee6dd40c7b756b986fca10942c9924369622fd08f87379ea3ddff81314341189" } } ], "extra": [ 1, 8, 26, 231, 227, 84, 242, 18, 155, 24, 51, 71, 96, 210, 63, 233, 78, 105, 34, 234, 138, 57, 255, 244, 214, 139, 57, 132, 107, 56, 6, 42, 27, 2, 17, 0, 0, 0, 2, 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