Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cef9ec89fafba07142894f30939bbf4bf67756f51a39417f5a52490270446d2

Tx prefix hash: be45b3f61509d7d972c3ab199aabdfc661ed5d8a4443e06a0adec5ffd70c9ad6
Tx public key: 418856f8acdf362a414d95bfb2c54888dec971dfd4f44549cb5cb954c8417fa9
Timestamp: 1672469925 Timestamp [UCT]: 2022-12-31 06:58:45 Age [y:d:h:m:s]: 01:339:18:30:11
Block: 664366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503870 RingCT/type: yes/0
Extra: 01418856f8acdf362a414d95bfb2c54888dec971dfd4f44549cb5cb954c8417fa9021100000002e7ace25d000000000000000000

1 output(s) for total of 3.860820549000 dcy

stealth address amount amount idx
00: d71af9aa7acf3d5c4d28d0bc9237ce8e5d6587e595da764b75851ed209a4a8a1 3.860820549000 1105341 of 0

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": 664376, "vin": [ { "gen": { "height": 664366 } } ], "vout": [ { "amount": 3860820549, "target": { "key": "d71af9aa7acf3d5c4d28d0bc9237ce8e5d6587e595da764b75851ed209a4a8a1" } } ], "extra": [ 1, 65, 136, 86, 248, 172, 223, 54, 42, 65, 77, 149, 191, 178, 197, 72, 136, 222, 201, 113, 223, 212, 244, 69, 73, 203, 92, 185, 84, 200, 65, 127, 169, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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