Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de1d9f57dc731d521213a65b13371f0f6d54ed3feae38126245647da79c55666

Tx prefix hash: 888ae79cdaa0eef640f6e53628a0d7a8e2175ba4231d52b4490df7c2eea2a09b
Tx public key: 80625d87e990d657c79c8b3e7068cd8eab70206c1955c389f3308b7ec1c3163b
Timestamp: 1751749512 Timestamp [UCT]: 2025-07-05 21:05:12 Age [y:d:h:m:s]: 00:136:17:09:00
Block: 1319491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96080 RingCT/type: yes/0
Extra: 0180625d87e990d657c79c8b3e7068cd8eab70206c1955c389f3308b7ec1c3163b02110000000501491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f03b8095f04f18aa0d71d966b56aac7ac09ff471d6cd9b896085c1f2e0277590 0.600000000000 1807184 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": 1319501, "vin": [ { "gen": { "height": 1319491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f03b8095f04f18aa0d71d966b56aac7ac09ff471d6cd9b896085c1f2e0277590" } } ], "extra": [ 1, 128, 98, 93, 135, 233, 144, 214, 87, 199, 156, 139, 62, 112, 104, 205, 142, 171, 112, 32, 108, 25, 85, 195, 137, 243, 48, 139, 126, 193, 195, 22, 59, 2, 17, 0, 0, 0, 5, 1, 73, 31, 136, 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