Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e08982b54214fca96ea58e86d4efbb7c1fc3d93e3b9053c5376efcc358b3c36

Tx prefix hash: b5bacb3cf84d990622b3bbbb6dd6251861a75b01b692ee20bb2045a0c52aa4a9
Tx public key: 52bc0d65a83b79e151c5df233d69eacc8e98312b9cdf79645526a3717aeb23ac
Timestamp: 1766101923 Timestamp [UCT]: 2025-12-18 23:52:03 Age [y:d:h:m:s]: 00:013:23:24:48
Block: 1436627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10010 RingCT/type: yes/0
Extra: 0152bc0d65a83b79e151c5df233d69eacc8e98312b9cdf79645526a3717aeb23ac0211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44e4ce7e56bfa8687130bf9f374ca31155e535e1bf6b2eac310e17f2e872fe28 0.600000000000 1925432 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": 1436637, "vin": [ { "gen": { "height": 1436627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44e4ce7e56bfa8687130bf9f374ca31155e535e1bf6b2eac310e17f2e872fe28" } } ], "extra": [ 1, 82, 188, 13, 101, 168, 59, 121, 225, 81, 197, 223, 35, 61, 105, 234, 204, 142, 152, 49, 43, 156, 223, 121, 100, 85, 38, 163, 113, 122, 235, 35, 172, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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