Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4154c5feb1fb1de439e2a5be0cf7f1b725e36c6e09369b019d6c8904328243d

Tx prefix hash: f417f78b9113a9f429a0ad80e1ac01e527b5d984700ac8e021467561ccb4167d
Tx public key: e559694623b8d3a700186deab63ecf3d7b88ddef5a4c11a6cb523b97a484c2dd
Timestamp: 1704267425 Timestamp [UCT]: 2024-01-03 07:37:05 Age [y:d:h:m:s]: 01:318:08:45:10
Block: 927117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486370 RingCT/type: yes/0
Extra: 01e559694623b8d3a700186deab63ecf3d7b88ddef5a4c11a6cb523b97a484c2dd02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a029556515be493cf90f3c6fab8d726e4d035bfda4daee003475c1ee048f3e97 0.600000000000 1384921 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": 927127, "vin": [ { "gen": { "height": 927117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a029556515be493cf90f3c6fab8d726e4d035bfda4daee003475c1ee048f3e97" } } ], "extra": [ 1, 229, 89, 105, 70, 35, 184, 211, 167, 0, 24, 109, 234, 182, 62, 207, 61, 123, 136, 221, 239, 90, 76, 17, 166, 203, 82, 59, 151, 164, 132, 194, 221, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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