Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 895c3ffb187a4691916f2f43a874df356d32548bf441d912d65526443a25d824

Tx prefix hash: e2ec8c1c8e81dc005551434f471e5f3f9a8f51219f9490752a15e2438c6e8b2c
Tx public key: c53dda1829a90a8eb909946e0837786b4de58bb2ecd3cf0bce39d75e5964a7eb
Timestamp: 1728497390 Timestamp [UCT]: 2024-10-09 18:09:50 Age [y:d:h:m:s]: 01:039:10:59:55
Block: 1128003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286585 RingCT/type: yes/0
Extra: 01c53dda1829a90a8eb909946e0837786b4de58bb2ecd3cf0bce39d75e5964a7eb02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4daae9e1e6a02106fd159af2eeb068e328c70d1d3f19a29b6abfc34dcfcd24d0 0.600000000000 1610818 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": 1128013, "vin": [ { "gen": { "height": 1128003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4daae9e1e6a02106fd159af2eeb068e328c70d1d3f19a29b6abfc34dcfcd24d0" } } ], "extra": [ 1, 197, 61, 218, 24, 41, 169, 10, 142, 185, 9, 148, 110, 8, 55, 120, 107, 77, 229, 139, 178, 236, 211, 207, 11, 206, 57, 215, 94, 89, 100, 167, 235, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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