Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73385d48e15efc572ac3f314a560c03ea0f434081e373891fa1a6eab14f31f8a

Tx prefix hash: 5c2be4beb642d69edf6da05bc5b973ee58c483752e2f420bc5340fadbcd725c7
Tx public key: 6ca91f0e9b9762c1befd28be69c0957fd00a7f9605add114e75d4f6c2b71ec81
Timestamp: 1711549909 Timestamp [UCT]: 2024-03-27 14:31:49 Age [y:d:h:m:s]: 01:029:22:21:48
Block: 987527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282354 RingCT/type: yes/0
Extra: 016ca91f0e9b9762c1befd28be69c0957fd00a7f9605add114e75d4f6c2b71ec810211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eb3587153b855a0dd5ce42e4ae7f16275ca229f185407ee38eaf298a6d1171f 0.600000000000 1447778 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": 987537, "vin": [ { "gen": { "height": 987527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eb3587153b855a0dd5ce42e4ae7f16275ca229f185407ee38eaf298a6d1171f" } } ], "extra": [ 1, 108, 169, 31, 14, 155, 151, 98, 193, 190, 253, 40, 190, 105, 192, 149, 127, 208, 10, 127, 150, 5, 173, 209, 20, 231, 93, 79, 108, 43, 113, 236, 129, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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