Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 229438abfeb17fd8f925b3403990734c3ba8d6ff648ebf002af98d8417d5e76a

Tx prefix hash: 19d1a0c54a2f3bda65b7892e28a69299358151df76f4058129d58e6d0c222af8
Tx public key: 750cbe33676e14a6c57b3dda3f1d5d3501b8ed15332ec63fd3aa0545d99b09be
Timestamp: 1714124934 Timestamp [UCT]: 2024-04-26 09:48:54 Age [y:d:h:m:s]: 00:203:00:37:44
Block: 1008849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145337 RingCT/type: yes/0
Extra: 01750cbe33676e14a6c57b3dda3f1d5d3501b8ed15332ec63fd3aa0545d99b09be02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b69ec8c9f0e8d4d3bd529372684a295617a05a0055273ea15cfc56fb422650ab 0.600000000000 1470335 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": 1008859, "vin": [ { "gen": { "height": 1008849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b69ec8c9f0e8d4d3bd529372684a295617a05a0055273ea15cfc56fb422650ab" } } ], "extra": [ 1, 117, 12, 190, 51, 103, 110, 20, 166, 197, 123, 61, 218, 63, 29, 93, 53, 1, 184, 237, 21, 51, 46, 198, 63, 211, 170, 5, 69, 217, 155, 9, 190, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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