Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eba1b1b7b86c17ad380ae631bd8fb99baaab7edfd663ff375ddd9f182ab39855

Tx prefix hash: 8df1cde477088fc62b3bb4aa6be3d0fbcd7c0761b4e9cd2a03ada529ed5b95b5
Tx public key: 9120f438d1298fe5e6375263bcbeeb00e30af97d0c436ed92a78b50ef5b9c7b8
Timestamp: 1736583302 Timestamp [UCT]: 2025-01-11 08:15:02 Age [y:d:h:m:s]: 00:089:14:34:51
Block: 1194900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63819 RingCT/type: yes/0
Extra: 019120f438d1298fe5e6375263bcbeeb00e30af97d0c436ed92a78b50ef5b9c7b8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d41b234c90b2ea15acfba6b4c425ea7ce6aca820a6652af433fc1296c52be45 0.600000000000 1681479 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": 1194910, "vin": [ { "gen": { "height": 1194900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d41b234c90b2ea15acfba6b4c425ea7ce6aca820a6652af433fc1296c52be45" } } ], "extra": [ 1, 145, 32, 244, 56, 209, 41, 143, 229, 230, 55, 82, 99, 188, 190, 235, 0, 227, 10, 249, 125, 12, 67, 110, 217, 42, 120, 181, 14, 245, 185, 199, 184, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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