Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab6d60e02c4804bb358f3715f54f8dd405c2d00779e7f0123afe6acf48993e90

Tx prefix hash: 2003aa322b80297f40bae71bf7a22923a91f6ad096f55436fbbe1b64f78ef399
Tx public key: d8540232b8c1cb9132de1a29003edab4680b10b56c51e91a8d7b1c22c72d59cf
Timestamp: 1744911339 Timestamp [UCT]: 2025-04-17 17:35:39 Age [y:d:h:m:s]: 00:217:19:28:18
Block: 1263568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153393 RingCT/type: yes/0
Extra: 01d8540232b8c1cb9132de1a29003edab4680b10b56c51e91a8d7b1c22c72d59cf021100000006dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ad64a4a91b29964ca02c5c478317fa3cd80efc417ec3a90fa2a3660d7b8b15e 0.600000000000 1750759 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": 1263578, "vin": [ { "gen": { "height": 1263568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ad64a4a91b29964ca02c5c478317fa3cd80efc417ec3a90fa2a3660d7b8b15e" } } ], "extra": [ 1, 216, 84, 2, 50, 184, 193, 203, 145, 50, 222, 26, 41, 0, 62, 218, 180, 104, 11, 16, 181, 108, 81, 233, 26, 141, 123, 28, 34, 199, 45, 89, 207, 2, 17, 0, 0, 0, 6, 219, 181, 113, 193, 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