Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d46cd590133f102f33589bd0b80c09831c5575ea8a3514c11a53f2b182a0133e

Tx prefix hash: fd2602aee03cedcce5bf5c57f34640fa9047db3749b1f802e7fbef255120f507
Tx public key: 073460cb59253bae4d5d9e9941dd8ca4a29c752a0520f45590f2cd66cc6ffc38
Timestamp: 1745779049 Timestamp [UCT]: 2025-04-27 18:37:29 Age [y:d:h:m:s]: 00:208:02:39:45
Block: 1270756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146458 RingCT/type: yes/0
Extra: 01073460cb59253bae4d5d9e9941dd8ca4a29c752a0520f45590f2cd66cc6ffc380211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e091dc412c2a657b1d6a5d6f9242c4cdaeb0b23926b7de4e5bf05a697da35f86 0.600000000000 1758001 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": 1270766, "vin": [ { "gen": { "height": 1270756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e091dc412c2a657b1d6a5d6f9242c4cdaeb0b23926b7de4e5bf05a697da35f86" } } ], "extra": [ 1, 7, 52, 96, 203, 89, 37, 59, 174, 77, 93, 158, 153, 65, 221, 140, 164, 162, 156, 117, 42, 5, 32, 244, 85, 144, 242, 205, 102, 204, 111, 252, 56, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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